[servicefabricmanagedclusters] 2026-02-01#39563
Conversation
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.Comment generated by summarize-checks workflow run. |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
|
...abricManagedClusters/examples/2025-10-01-preview/ManagedClusterPutOperation_example_max.json
Outdated
Show resolved
Hide resolved
...agedClusters/preview/2025-10-01-preview/examples/ManagedClusterPutOperation_example_max.json
Outdated
Show resolved
Hide resolved
|
@iliu816 - I see that the no-recent-activity action must have removed the ARMSignedOff label. I'll put it back, since your PR already passed review previously. Couple of points:
|
We were previously asked to get a review before we started planning for deployment, so we started getting the ARM review much earlier. But sometimes there may be a complication, so we usually let the PR sit until we confirm that the rollout will proceed so customers don't find documentation for the api version if it isn't available to use yet. |
* initial copy of prev api version * 2026-02-01 init * add new version to readme.md * fix missed reference to previous api version * add skipManagedNsgAssignment * add BYOVNET to spellcheck override, fix example * add enableResilientEphemeralOsDisk to NodeTypeProperties --------- Co-authored-by: Mike Harder <mharder@microsoft.com>
…eneration - JS-5919238 (#37356) Configurations: 'specification/servicefabricmanagedclusters/resource-manager/Microsoft.ServiceFabric/ServiceFabricManagedClusters/tspconfig.yaml', API Version: 2026-02-01, SDK Release Type: stable, and CommitSHA: '57a2504930224552a409d9435d523e631a6c93e2' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5919238 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. **Release plan link:** [https://web.powerapps.com/apps/821ab569-ae60-420d-8264-d7b5d5ef734c?release-plan-id=2c8e6891-a411-f111-8406-000d3a5a7db7](https://web.powerapps.com/apps/821ab569-ae60-420d-8264-d7b5d5ef734c?release-plan-id=2c8e6891-a411-f111-8406-000d3a5a7db7) **Submitted by**: iliu@microsoft.com ## Release Plan Details - Release Plan: https://aka.ms/sdk-release-planner?release-plan-id=2c8e6891-a411-f111-8406-000d3a5a7db7 Spec pull request: Azure/azure-rest-api-specs#39563 Spec API version: 2026-02-01 --------- Co-authored-by: Ivy Liu <iliu@microsoft.com>
…eneration - JS-5919238 (Azure#37356) Configurations: 'specification/servicefabricmanagedclusters/resource-manager/Microsoft.ServiceFabric/ServiceFabricManagedClusters/tspconfig.yaml', API Version: 2026-02-01, SDK Release Type: stable, and CommitSHA: '57a2504930224552a409d9435d523e631a6c93e2' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5919238 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. **Release plan link:** [https://web.powerapps.com/apps/821ab569-ae60-420d-8264-d7b5d5ef734c?release-plan-id=2c8e6891-a411-f111-8406-000d3a5a7db7](https://web.powerapps.com/apps/821ab569-ae60-420d-8264-d7b5d5ef734c?release-plan-id=2c8e6891-a411-f111-8406-000d3a5a7db7) **Submitted by**: iliu@microsoft.com ## Release Plan Details - Release Plan: https://aka.ms/sdk-release-planner?release-plan-id=2c8e6891-a411-f111-8406-000d3a5a7db7 Spec pull request: Azure/azure-rest-api-specs#39563 Spec API version: 2026-02-01 --------- Co-authored-by: Ivy Liu <iliu@microsoft.com>
ARM (Control Plane) API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting helpsection at the bottom of this PR description.PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!
Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
Additional information
Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the
Generated ApiViewcomment added to this PR. You can use ApiView to show API versions diff.Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.
Getting help
Purpose of this PRandDue diligence checklist.write accessper aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Mergecomment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queuedstate, please add a comment with contents/azp run.This should result in a new comment denoting a
PR validation pipelinehas started and the checks should be updated after few minutes.